First of all, I've have tried search and yes I found a couple of threads around the issue but they didn't help at all. I've been fighting with this this a couple of weeks now and I'm starting to get really frustrated. I started using a network drive a while ago. Never been able to get it work on Windows 7. I have two PC's, one running Windows 7 Home Premium, the second Ultimate version, both x64 and Service Pack 1. Both computers facing the same problem, so I can't really use the network drive att all. The usb drive is connected to my WLAN router and shared via network. It does work and sharing can be done. The thing is, when accessing the drive via Windows I always get BSD with code STOP 0x00000027 (Parameter 1, 2, 3, 4) RDR_FILE_SYSTEM. Sometimes I get to use the drive for a while without crashing but usually BSD comes in a matter of seconds. There is this unfinished hotfix http://support.microsoft.com/kb/981109 but cant install it. It only says "Update does not apply to your system". With Linux/android devices theres no problem but I really need that network drive and my PC's. Anytime soon any progress going to happen with the issue that's been there apparently years allready..?

1. This hotfix is for Windows 7, but you have Windows 7 with SP1. That is why the hotfix may response in this way. 2. Run "sfc /scannow" to find if there is no verification problem. 3. Would you upload minidump file into SkyDrive or similat cloud repository? Regards Milos

Hi, Maybe there is one AutoRun *.exe file which is malware in your network drive. You should scan and remove malware from your USB drive first. If this issue persists, you may plug it to your Windows 7 computer with USB directly and check it again. May I know your router supports USB drive If so, to replace a new one or flash USB for testing. Meanwhile, you may check *.dump files. The log file will be %systemroot%\Minidump which is normally C:\windows\Minidump How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263/en-uIvan-Liu TechNet Community Support

Hello, Bug Check Code 0x27: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557446%28v=vs.85%29.aspx Please check that you have enough RAM. If not then you will have to add an additional one. Please start proceeding like that: Update all possible driversUninstall all unused programsRun chkdsk /r /f and sfc /scannowPerform a clean boot: http://support.microsoft.com/kb/929135Disable temporary all security softwares you haveRun memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance If this does not help then use Microsoft Skydrive to upload dump files (c:\windows\minidump). Once done, post a link here. You can also contact Microsoft CSS for assistance. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Did run chksk and sfc / scannow, no error were found. Memtest did find errors and I replased the faulty Ram. I Ran it again and there where no errors. I also re-installed Windows but the BSD is still there. Latest Minidumb My system has 8GB of RAM, should be enought.

Did run chksk and sfc / scannow, no error were found. Memtest did find errors and I replased the faulty Ram. I Ran it again and there where no errors. I also re-installed Windows but the BSD is still there. Latest Minidumb My system has 8GB of RAM, should be enought. Set the folder for public access. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Should work now. Minidump

So any word on this? The issue is still there. Can't really use my netword drive now and it's a must as my second PC is an all-in-one with only 64GB SSD so I need the extra storage.

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* RDR_FILE_SYSTEM (27) If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined as follows: RDBSS_BUG_CHECK_CACHESUP = 0xca550000, RDBSS_BUG_CHECK_CLEANUP = 0xc1ee0000, RDBSS_BUG_CHECK_CLOSE = 0xc10e0000, RDBSS_BUG_CHECK_NTEXCEPT = 0xbaad0000, Arguments: Arg1: 00000000baad0073 Arg2: fffff880076381f8 Arg3: fffff88007637a50 Arg4: fffff80002eace68 Debugging Details: ------------------ EXCEPTION_RECORD: fffff880076381f8 -- (.exr 0xfffff880076381f8) ExceptionAddress: fffff80002eace68 (nt!CcGetVirtualAddress+0x00000000000000f8) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 CONTEXT: fffff88007637a50 -- (.cxr 0xfffff88007637a50) rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=000000000bd3e020 rdi=0000000000000001 rip=fffff80002eace68 rsp=fffff88007638430 rbp=fffffa8008c71a20 r8=fffff88007638500 r9=fffff88007638590 r10=0000000000000002 r11=00000000000002fe r12=0000000000000000 r13=0000000000000001 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210246 nt!CcGetVirtualAddress+0xf8: fffff800`02eace68 488b34c8 mov rsi,qword ptr [rax+rcx*8] ds:002b:00000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c9100 0000000000000000 FOLLOWUP_IP: rdbss!RxCommonRead+db1 fffff880`02dd7661 403ac7 cmp al,dil FAULTING_IP: nt!CcGetVirtualAddress+f8 fffff800`02eace68 488b34c8 mov rsi,qword ptr [rax+rcx*8] BUGCHECK_STR: 0x27 LAST_CONTROL_TRANSFER: from fffff80003180b02 to fffff80002eace68 STACK_TEXT: fffff880`07638430 fffff800`03180b02 : fffff880`00000000 00000000`00000000 fffff880`07638500 fffff880`07638590 : nt!CcGetVirtualAddress+0xf8 fffff880`076384c0 fffff880`02dd7661 : 00000000`00000000 00000000`00000005 fffff880`076386f0 fffff880`02dc3001 : nt!CcCopyRead+0x132 fffff880`07638580 fffff880`02dab684 : fffffa80`094d3010 00000000`0bd3e020 01cd23b5`92d97d00 00000000`00000166 : rdbss!RxCommonRead+0xdb1 fffff880`076386b0 fffff880`02dc8b44 : fffffa80`098430e0 fffffa80`08133603 00000000`010f9f53 fffff880`011401b5 : rdbss!RxFsdCommonDispatch+0x870 fffff880`076387a0 fffff880`054562cc : fffffa80`098430e0 fffff880`010f9f53 fffffa80`098431f8 fffffa80`08133620 : rdbss!RxFsdDispatch+0x224 fffff880`07638810 fffff880`0195e271 : fffffa80`08d86a90 fffffa80`098430e0 fffffa80`08e726b0 fffff8a0`0034fa60 : mrxsmb!MRxSmbFsdDispatch+0xc0 fffff880`07638850 fffff880`0195c138 : fffff8a0`0034fa60 fffffa80`08d86a90 00000000`00000001 00000000`00000000 : mup!MupiCallUncProvider+0x161 fffff880`076388c0 fffff880`0195cb0d : fffffa80`098430e0 fffff880`0195a110 fffffa80`06e1d540 00000000`00000000 : mup!MupStateMachine+0x128 fffff880`07638910 fffff880`010f5bcf : fffffa80`09843288 fffffa80`08d86a90 fffff880`076389a0 fffffa80`09395d30 : mup!MupFsdIrpPassThrough+0x12d fffff880`07638960 fffff880`010f46df : fffffa80`07184b80 00000000`00000001 fffffa80`07184b00 fffffa80`098430e0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`076389f0 fffff800`0319effb : 00000000`00000000 fffffa80`06e1d540 00000000`00000001 fffffa80`098430e0 : fltmgr!FltpDispatch+0xcf fffff880`07638a50 fffff800`031808a3 : fffffa80`06e1d540 fffffa80`06e1d540 fffffa80`06e1d540 fffff880`02f64180 : nt!IopSynchronousServiceTail+0xfb fffff880`07638ac0 fffff800`02e96f13 : 00000000`00000b04 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631 fffff880`07638bb0 00000000`7745137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0370e048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7745137a SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: rdbss!RxCommonRead+db1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdbss IMAGE_NAME: rdbss.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79497 STACK_COMMAND: .cxr 0xfffff88007637a50 ; kb FAILURE_BUCKET_ID: X64_0x27_rdbss!RxCommonRead+db1 BUCKET_ID: X64_0x27_rdbss!RxCommonRead+db1 Followup: MachineOwner -------------------------------------- Please finish what I already suggested: Update all possible driversUninstall all unused programsPerform a clean boot: http://support.microsoft.com/kb/929135Disable temporary all security softwares you have This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Please finish what I already suggested: Update all possible drivers - DoneUninstall all unused programs - There isn't any. As I said, a fresh Windows installation.Disable temporary all security softwares you have - Done No effect. Perform a clean boot: http://support.microsoft.com/kb/929135 - I'll try this later today.

Well I almost forgot this. Clean boot did not help at all. First the same 0x27 Error but then I saw a new bluescreen type: IRQL_NOT_LESS_OR_EQUAL. I'm sure this is not a hardware issue as with Ubuntu-Linux things runs smoothly. Also, stil happens with two computers with different hardware. I'm done with this. Perhaps I'll go for a Mac soon.